Post-write scan operations for interlaced magnetic recording

ABSTRACT

A storage device includes a data degradation management module that tracks a risk of data degradation by incrementing a track write counter of a first data track responsive to each data write command to a second data track, such as a data track directly adjacent to the first data track. If a count of the track write counter exceeds a count threshold, one or more post-write scan operations are performed to assess and/or repair data degradation of the first data track.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation application of U.S. application Ser. No. 14/688,667, issued as U.S. Pat. No. 9,324,362, which claims benefit of priority to U.S. Provisional Application No. 62/083,696, entitled “Interlaced Magnetic Recording in HAMR Devices” and filed on Nov. 24, 2014, and also to U.S. Provisional Patent Application No. 62/083,732, entitled “Interlaced Magnetic Recording” and filed on Nov. 24, 2014, and also to U.S. Provisional Patent Application No. 62/110,039, entitled “Post-Write Scan Operations for Interlaced Magnetic Recording” and filed on Jan. 30, 2015. Each of these applications is specifically incorporated by reference for all that they disclose or teach.

BACKGROUND

As requirements for data storage density increase for magnetic media, cell size decreases. One technique for adapting the magnetic medium to utilize smaller cells while preventing adjacent data from being overwritten during a write operation is shingled magnetic recording (SMR). SMR allows for increased areal density capability (ADC) as compared to conventional magnetic recording (CMR) but at the cost of some performance ability. As used herein, CMR refers to a system that allows for random data writes to available cells anywhere on a magnetic media. In contrast to CMR systems, SMR systems are designed to utilize a write element with a write width that is larger than a defined track pitch. As a result, changing a single data cell within a data track entails re-writing a corresponding group of shingled (e.g., sequentially increasing or decreasing) data tracks.

Another technique for increasing ADC of the magnetic medium is interlaced magnetic recording (IMR). IMR makes use of alternating data tracks of variable written track width and variable linear densities. For example, odd-numbered data tracks may have a wide written track width and a first linear density, while even-numbered data tracks have a narrower written track width and a second, different linear density. Track boundaries can be defined such that tracks of narrower width slightly overlap the underlying written tracks of wider track width. In IMR systems, some data tracks are randomly writable and other data tracks are not randomly writable.

In each of the above-described types of data storage systems, a risk of data degradation exists due to an effect known as adjacent track interference (ATI). Some systems implement one or more integrity-assurance techniques, such as direct offline scans or periodic track re-writes, to monitor and reduce a severity data degradation. Better data management techniques are desired to reduce a strain on processing resources and increase storage device performance while achieving or improving upon the ADC of these existing systems.

BRIEF DESCRIPTIONS OF THE DRAWINGS

FIG. 1 illustrates an example data storage device including a transducer head assembly for writing data on a magnetic storage medium.

FIG. 2 illustrates an example data management system implementing interlaced magnetic recording (IMR) storage techniques.

FIG. 3A illustrates example post-write scan operations of a data management system implementing IMR storage techniques.

FIG. 3B illustrates additional example post-write scan operations of the data management system of FIG. 3A.

FIG. 4 illustrates example operations for monitoring and rectifying data degradation in a data management system implementing IMR storage techniques.

SUMMARY

According to one implementation, a method provides for incrementing a track write counter of a first data track responsive to a data write command to a second data track and reading the first data track if a count of the track write counter satisfies a threshold. If a number of read errors detected during the reading of the first data track satisfies an error threshold, the method further provides for re-writing the first data track and at least one directly adjacent data track.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. These and various other features and advantages will be apparent from a reading of the following Detailed Description.

DETAILED DESCRIPTION

FIG. 1 illustrates an example data storage device 100 including a transducer head assembly 120 for writing data on a magnetic storage medium 108. Although other implementations are contemplated, the magnetic storage medium 108 is, in FIG. 1, a magnetic storage disc on which data bits can be recorded using a magnetic write pole (e.g., a write pole 130) and from which data bits can be read using a magnetoresistive element (not shown). As illustrated in View A, the storage medium 108 rotates about a spindle center or a disc axis of rotation 112 during rotation, and includes an inner diameter 104 and an outer diameter 102 between which are a number of concentric data tracks 110. Information may be written to and read from data bit locations in the data tracks on the storage medium 108.

The transducer head assembly 120 is mounted on an actuator assembly 109 at an end distal to an actuator axis of rotation 114. The transducer head assembly 120 flies in close proximity above the surface of the storage medium 108 during disc rotation. The actuator assembly 109 rotates during a seek operation about the actuator axis of rotation 112. The seek operation positions the transducer head assembly 120 over a target data track for read and write operations.

In one implementation employing heat-assisted magnetic recording (HAMR) (e.g., View B), magnetic grains on the storage medium 108 are temporarily heated during the recording process to selectively lower magnetic coercivity in a tightly focused area of the storage medium 108 that substantially corresponds to an individual data bit. The heated region is then encoded with the recorded data bit based on the polarity of an applied magnetic write field. After cooling, the magnetic coercivity substantially returns to its pre-heating level, thereby stabilizing the magnetization for that data bit. This write process is repeated for multiple data bits on the storage medium, and such data bits can be read using a magneto-resistive read head.

Referring to View B, the transducer head assembly 120 includes, among other features, a heat source 132 (e.g., a laser) coupled to a submount assembly 134. Light from the heat source 132 is directed into a waveguide 138 mounted to a slider 140. Light exiting the waveguide is focused, via a Near Field Transducer (NFT) 144, and applied to a bit location on the storage medium 108 just before the bit location is subjected to a magnetic pulse generated by the write pole 130. As an air-bearing surface 146 of the slider 140 “flies” across the surface of the storage medium 108, the write pole 130 selectively magnetizes the underlying magnetic grains of the storage medium 108.

View C illustrates a magnified view 152 of magnetic polarized regions (e.g., individual data bits or groupings of data bits of like polarity) recorded on storage medium 108 according to one write methodology of the magnetic storage device 100. The polarized regions are also referred to herein as “data bits” (e.g., data bits 127, 128), which each represent one or more individual data bits of a same state (e.g., 1s or 0s). For example, the data bit 127 is a magnetically polarized region representing multiple bits of a first state (e.g., “000”), while the data bit 128 is an oppositely polarized region representing one or more bits of a second state (e.g., a single “1”).

The data bits of the magnified view 152 illustrate data storage according to an interlaced magnetic recording (IMR) technique. IMR utilizes alternating data tracks of different written track widths arranged with slightly overlapping written track boundaries so that a center-to-center distance between directly adjacent tracks (e.g., the track pitch) is uniform across the surface of the magnetic medium 108. For example, the IMR technique shown in the magnified view 152 illustrates alternating data tracks of two different written track widths. A first series of alternating tracks (e.g., the tracks 158, 160, and 162) have a wider written track width than a second series of interlaced data tracks (e.g., 164 and 166).

In the magnified view 152, each wide data track of the first series is written before the narrow and directly adjacent data tracks of the second series. For example, the data track 160 is written before data is written to either of the data tracks 164 and 166. Data writes to the data tracks 164 and 166 overwrite outer edge portions of the data track 160; however, the data track 160 is still readable due to sufficient information retained in a center region of the data track 160.

Because each data track of wide written track width is written prior to directly adjacent data tracks of narrower written track width, the data tracks of the wider written track width (e.g., data tracks 158, 160, and 162) are also referred to herein as “bottom tracks,” while the alternating data tracks of narrower written width (e.g., the data tracks 164 and 166) are referred to herein as “top tracks.” In one implementation, the bottom tracks of wider written track width include data stored at a higher linear density than the top tracks of narrower written track width.

IMR can allow for higher areal recording densities than other conventional recording techniques. However, one consequence of IMR is that the bottom tracks (e.g., the data tracks 158, 160, and 162) are not randomly writable when data is stored on directly adjacent top data tracks. As used herein, a data track is “randomly writable” when the data track can be individually re-written multiple times without significantly degrading data on other adjacent data tracks. An adjacent data track is “significantly degraded” if reading the data track results in a number of read errors in excess of a maximum number of errors that can be corrected by a correction code (ECC) of the data storage device 100.

According to one implementation of the disclosed technology, a data write to a bottom data track entails reading data of any directly adjacent data tracks into a memory location and re-writing a group of data tracks in a single write operation. For example, re-writing the data track 160 may entail the following operations in the following order: (1) reading the immediately adjacent top data tracks 164 and 166 into a memory location; (2) writing the new data to the data track 160; and (3) subsequently writing data to the top data tracks 164 and 166 from the memory location.

In general, the top data tracks in the data storage device 100 are randomly writeable. For example, the data track 166 can be re-written up to some threshold number of times without significantly degrading data on the adjacent tracks 160 and 162. However, after many repeated re-writes of a top data track (such as the data track 166), data on the immediately adjacent data tracks (e.g., one or both bottom tracks 160 and 162) may become corrupted due to a gradual degradation effect known as adjacent track interference (ATI) (also referred to as adjacent track erasure (ATE)).

To mitigate and rectify the effects of ATI, a degradation management module 118 of the data storage device 100 implements certain data management techniques including systematic data scans and periodic track re-writes. In one implementation, the degradation management module 118 maintains track write counters for each of the bottom data tracks and increments each counter responsive to data write commands to one or more of the immediately adjacent top data tracks. For example, a track write counter for the data track 160 increments each time data is written to either of the directly adjacent top data tracks 164 and 166.

When a count value of a particular track write counter satisfies a predetermined count threshold, the degradation management module 118 reads the associated bottom data track and determines a number of resulting read errors. If the number of read errors exceeds an error threshold, the degradation management module 118 may elect to re-write data of the associated bottom data track and one or more immediately adjacent data tracks. Further details of this and other data management processes are described with respect to FIGS. 2-4 below.

The degradation management 120 includes software and/or hardware, and may be implemented in any tangible computer-readable storage media within or communicatively coupled to the storage device 100. The term “tangible computer-readable storage media” includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CDROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other tangible medium which can be used to store the desired information and which can be accessed by mobile device or computer. In contrast to tangible computer-readable storage media, intangible computer-readable communication signals may embody computer readable instructions, data structures, program modules or other data resident in a modulated data signal, such as a carrier wave or other signal transport mechanism. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.

FIG. 2 illustrates an example data management system 200 implementing IMR storage techniques. The data management system 200 includes a magnetic disc 202 including a number of substantially circular data tracks (e.g., data tracks 203-209) storing data at variable written track widths and linear densities. For example, the odd-numbered data tracks 203, 205, 207 and 209 (collectively, the “bottom data tracks”) store data at a first written track width and linear density while the even-numbered data tracks 204, 206, and 208 (collectively, the “top data tracks”) store data at a second written track width and linear density.

A read/write management module 222 manages read and write operations of the data management system 200 and ensures that each of the bottom data tracks of the magnetic disc 202 receives data before either of the directly-adjacent top data tracks. For example, the read/write management module 222 writes data to a bottom data track 205 before writing any data to either of the immediately adjacent and slightly overlapping top data tracks 204 and 206.

In general, the top data tracks can be individually (e.g., randomly) updated and re-written a threshold number of times without causing significant degradation to any of the bottom data tracks. In contrast, the bottom data tracks are not randomly writeable if directly adjacent to a data-storing top data track. For example, the bottom data track 205 is not randomly writable and updating the bottom data track 205 entails executing the following operations in the following order: (1) reading data of the top data tracks 204 and 206 into a memory location; (2) writing the bottom data track 205 to include the updated data; and (3) subsequently re-writing the data of the top data tracks 204 and 206 from the memory location.

Over time, ATI resulting from repeated data writes to one or more of the top data tracks can cause some data degradation on the immediately adjacent bottom data tracks. In general, a small degree of data degradation may be acceptable if the data is repairable via an error correction code (ECC) of the data management system 200. However, if the data degradation becomes too severe, the ECC may be unable to repair the data.

To address the aforementioned ATI concerns, a degradation management module 220 monitors data degradation and repairs data degradation on a continuous basis throughout the life of a storage device including the data management system 200. To help monitor severity of degradation at various places on the magnetic disc 200, the degradation management module 220 manages a number of write counters (e.g., write counters C1, C2, C3, and C4) that are each associated with one of the bottom data tracks (e.g., 203, 205, 207 and 209, respectively).

When data is received on one of the top data tracks, the degradation management module 220 increments track write counter(s) of any of the bottom tracks directly adjacent to the top track receiving the data. For example, the write counter C1 of the bottom data track 203 increments each time the top data track 204 receives data; the write counter C2 of the bottom data track 205 increments each time either of the top data tracks 204 and 206 receive data; the write counter C3 of the bottom data track 207 increments each time either of the top data tracks 206 and 208 receive data; and the write counter C4 of the bottom data track 209 increments each time the top data track 208 receives data. Each of the counters C1, C2, C3, and C4 is associated with a predetermined count threshold. When a count of any of the track write counters equals the predetermined count threshold, the degradation management module 220 initiates one or more post-write scan operations to assess and, optionally, to repair data degradation. The predetermined count threshold may be the same or different for each of the different write track counters. In one implementation, some regions of the magnetic disc 202 store higher priority data than other regions. Write track counters associated with the high priority regions have a lower count threshold than lower priority regions. In another implementation, all write track counters in the data management system 200 have a same predetermined count threshold.

In one implementation, the degradation management module 220 initiates a direct offline scan (DOS) of a bottom data track when the associated track write counter reaches a count threshold. For example, the degradation management module 220 may initiate a DOS of the data track 205 when a count of the track write counter C2 equals a predetermined count threshold.

A DOS, also referred to as a defective data scan, is one example of a post-write scan operation. The purpose of the DOS is to measure degradation to a particular data track, such as degradation that is due to ATI. During the DOS, data is read back from a data track. An error correction code (ECC) repairs errors in the read data to the extent possible, and the degradation management module 220 counts a number of correctable read errors. If the number of correctable read errors satisfies an error threshold, the degradation management module 220 may elect to re-write the data of that data track to repair data degradation.

Other post-write scan operations include, for example, re-writing a data track if a DOS indicates the data track is significantly degraded, resetting a write counter for the re-written data track, or incrementing one or more write counters responsive to re-writes of any top data tracks. Additional post-write scan operations performed by the degradation management module are described with respect to FIGS. 3A and 3B, below.

FIG. 3A illustrates example post-write scan operations of a data management system 300 implementing IMR storage techniques. The data management system 300 includes a magnetic disc with a number of substantially circular data tracks (e.g., data tracks 303-309) storing data at variable written track widths and linear densities. For example, odd-numbered data tracks 303, 305, 307 and 309 (collectively, the “bottom data tracks”) store data at a first written track width and linear density while even-numbered data tracks 304, 306, and 308 (collectively, the “top data tracks”) store data at a second written track width and linear density.

Over time, ATI resulting from repeated data writes to one or more of the top data tracks can cause some data degradation on the associated, directly adjacent bottom data tracks. For example, a repeated data write to the data track 304 can cause degradation to the directly-adjacent bottom data tracks 303 and 305.

To help monitor a severity of degradation at various radial positions on the disc, a data degradation management module (not shown) of the data management system 300 manages a write counter (e.g., write counters C1, C2, C3, and C4) in association with each of the bottom data tracks 303, 305, 307 and 309. Each time data is received on a top data track, track write counters increment in association with any bottom data tracks immediately adjacent to the top data track receiving the data. For example, the track write counter C2 of the data track 305 increments from an existing value (e.g., 9) to a new value (e.g., 10, as shown) when data is written to the top data track 306. In addition, a write to the data track 306 also increments the track write counter C3 of track 307.

In one implementation, the degradation management module of the data management system 300 initiates a DOS of a bottom data track when the associated track write counter reaches a count threshold. For example, a DOS may read data from the data track 305 when a count of the track write counter C2 equals ‘10’ (as shown in FIG. 3A).

Responsive to the DOS, the degradation management module determines a number of read errors that occurred in reading the data track 305. If the total number of read errors equals or exceeds an error threshold, the degradation management module 320 performs further post-write scan operations, as described below with respect to FIG. 3B. If the total number of read errors does not equal or exceed an error threshold, no further post-write scan operations are performed.

FIG. 3B illustrates a rewrite of data tracks 304, 305, and 306 responsive to a determination that a DOS scan of the data track 305 results in a number of read errors satisfying an error threshold. Re-writing the data track 305 is a multi-step process including the following operations in the following order: (1) reading data of the data tracks 304, 305, and 306 into a memory cache; (2) re-writing data of the data track 305 from the memory cache; and (3) re-writing data to the data tracks 304 and 306 from the memory cache.

Responsive to a re-write of any individual bottom data track, an associated track write counter is reset to a default value. For example, the re-write of the data track 305 resets the associated track write counter C2 from ‘10’ to ‘0.’ Further, the re-write of the top data track 304 increments the track write counter C1 of the bottom data track 303 from ‘6’ to ‘7’ and also increments the track write counter C2 of the bottom data track 305 to increment from ‘0’ to ‘1.’ Similarly, the re-write of the data track 306 increments the track write counter C3 of the bottom data track 307 from ‘5’ to ‘6’ and also increments track write counter C2 of the bottom data track 305 from ‘1’ to ‘2.’ In the illustrated manner, the data management system 300 monitors and repairs data degradation across the surface of the magnetic disc, periodically repairing data degradation before such degradation becomes significant.

In one implementation, the degradation management module performs post-write scan operations on more than one data track at once. If, for example, the write track counters for two or more adjacent odd data tracks (e.g., data tracks 305 and 307) reach a count threshold at the same time, the degradation management module may perform a DOS on each of the adjacent odd data tracks and optionally re-write more than three data tracks at once.

For example, the data tracks 305 and 307 may have associated write track counters that reach a count threshold simultaneously. In this situation, the degradation management module reads both of the data tracks 305 and 307 and determines, for both data tracks, whether a resulting number of read errors exceeds an error threshold.

If the resulting number of read errors exceeds the error threshold for one of the data track, such as data track 305 but not the data track 307, the data track 305 is re-written along with adjacent top data tracks 304 and 306, as described above. The data track 307 is not re-written at this time. In one implementation, however, the track write counter C3 of the data track 307 is re-set to another value after the DOS terminates, even if the data track 307 is not re-written. This new value of the write track counter C3 depends on the number of read errors detected during the DOS of the data track and is a value that is less than the predetermined count threshold (e.g., 10) but greater than the default reset value (e.g., 0). If, for example, there are relatively few read errors detected during the DOS of the data track 307, the write track counter C3 may be re-set to a medium-low value (e.g., 1). However, if, there are a large number of read errors detected, the write track counter C3 may be set to a medium-high value (e.g., 6).

If, on the other hand, the DOS of the data tracks 305 and 307 results in a number of read errors exceeding the error threshold for both of the data tracks 305 and 307, the degradation management module re-writes a group of more than three data tracks (e.g., 304-308) all at once. For example, the degradation management module may perform the following operations in the following order: (1) read the data tracks 304, 306, and 308 into a memory location; (2) re-write the data tracks 305 and 307; and (3) re-write the data tracks 304, 306, and 308.

If, however, the resulting number of read errors exceeds the error threshold for both of the adjacent odd data tracks 305 and 307, the degradation management module re-writes a group of more than three data tracks (e.g., 304-308) all at once. For example, the degradation management module may perform the following operations in the following order: (1) read the data tracks 304, 306, and 308 into a memory location; (2) re-write the data tracks 305 and 307; and (3) re-write the data tracks 304, 306, and 308.

FIG. 4 illustrates example operations 400 for monitoring and rectifying data degradation in a data management system implementing IMR storage techniques. The data management system includes a plurality of track write counters that each quantify a risk of degradation for an associated data track in a series of alternating data tracks on the magnetic disc. In at least one implementation, the data management system does not include track write counters quantifying a risk of degradation for any of a series of interlaced data tracks making up alternating (e.g., every other) track on the storage medium. For example, write counters may be associated with each of the odd-numbered data tracks but not associated with any of the even-numbered data tracks.

A first write operation 405 writes data to a first data track. For example, the first data track may be a defined “top” data track with edges that slightly overlap and overwrite outer boundaries of two adjacent previously-written “bottom” data tracks (hereinafter “second” and “third” data tracks). When the first (e.g., top) data track is written, a chance of degradation of the second and third (e.g., bottom) data tracks increases. To track this increased likelihood, an incrementation operation 410 increments track write counters of the second data track and the third data track by a predetermined amount (e.g., 1 count).

A determination operation 415 determines whether a count of any of the track write counters satisfies a count threshold. If none of the track write counters has a count value satisfying the count threshold, a waiting operation 445 waits for the next write operation. On the other hand, if the determination operation 415 determines that any one of the track write counters in the data management system has a count value satisfying the count threshold, one or more post-write scan operations are performed.

A reading operation 420 reads the data track corresponding to the counter satisfying the threshold (hereinafter, the degraded data track). A determination operation 425 then determines whether the reading operation 420 of the degraded data track results in a number of read errors satisfying an error threshold. If the reading operation 420 does not result in a number of read errors satisfying a count threshold, the waiting operation 445 resumes to wait for the next write operation.

If, on the other hand, the determination operation 425 determines that the reading operation 420 results in a number of read errors satisfying an error threshold, a re-write operation 430 rewrites the degraded data track and its directly adjacent data tracks. In one implementation, the re-writing of the degraded data track entails the following operations in the following order (1) reading the degraded data track and the directly adjacent data tracks into a memory location; (2) re-writing, from memory, the data of the degraded data track; and (3) re-writing, from memory, the data of the directly adjacent top data tracks.

Responsive to a re-write of the degraded data track, a reset operation 435 resets the track write counter of the degraded data track to a default value (e.g., 0). An incrementation operation 440 increments track write counters of various data tracks responsive to the re-write operation 430. In one implementation, the track write counter of the degraded data track is incremented twice to account for re-writes of each of the directly adjacent top data tracks. Further, track write counters are incremented for each of the bottom data tracks on either side of the degraded data track and separated from the degraded data track by one interlaced (top) data track (see, e.g., track write counters 303 and 307 incrementing responsive to rewrite of data track 305 in FIG. 3B). After the incrementation operation 440, the waiting operation 445 resumes to wait for the next write operation.

The embodiments of the disclosed technology described herein are implemented as logical steps in one or more computer systems. The logical operations of the presently disclosed technology are implemented (1) as a sequence of processor-implemented steps executing in one or more computer systems and (2) as interconnected machine or circuit modules within one or more computer systems. The implementation is a matter of choice, dependent on the performance requirements of the computer system implementing the disclosed technology. Accordingly, the logical operations making up the embodiments of the disclosed technology described herein are referred to variously as operations, steps, objects, or modules. Furthermore, it should be understood that logical operations may be performed in any order, adding and omitting as desired, unless explicitly claimed otherwise or a specific order is inherently necessitated by the claim language.

The above specification, examples, and data provide a complete description of the structure and use of exemplary embodiments of the disclosed technology. Since many embodiments of the disclosed technology can be made without departing from the spirit and scope of the disclosed technology, the disclosed technology resides in the claims hereinafter appended. Furthermore, structural features of the different embodiments may be combined in yet another embodiment without departing from the recited claims. 

What is claimed is:
 1. One or more tangible computer-readable storage media encoding computer-executable instructions for executing on a computer system a computer process, the computer process comprising: incrementing a track write counter of a first data track responsive to a data write command to a second data track but not incrementing any track write counters responsive to a data write to the first data track.
 2. The tangible computer-readable storage media of claim 1, wherein the computer process further comprises: re-writing data of the first data track and data of at least one directly adjacent data track based on a count value of the track write counter.
 3. The tangible computer-readable storage media of claim 1, wherein the computer process further comprises: reading the first data track if a count of the track write counter satisfies a count threshold; and re-writing data of the first data track if a number of read errors detected during the reading of the first data track satisfies an error threshold.
 4. The tangible computer-readable storage media of claim 1, wherein the track write counter quantifies a risk of data degradation of the first data track.
 5. The tangible computer-readable storage media of claim 1, wherein the first data track is directly adjacent to the second data track.
 6. The tangible computer-readable storage media of claim 2, wherein re-writing the first data track and at least one directly adjacent data track further comprises: re-writing data of data tracks directly adjacent to the first data track.
 7. The tangible computer-readable storage media of claim 2, wherein the computer process further comprises: resetting the track write counter of the first data track to a default value.
 8. A method comprising: incrementing a first track write counter responsive to a data write to a first data track but not incrementing any track write counters responsive to a data write to a second data track directly adjacent to the first data track.
 9. The method of claim 8, wherein the method further comprises: re-writing data of the first data track and data of the second data based on a count value of the first track write counter.
 10. The method of claim 8, wherein the method further comprises: reading the first data track if a count of the track write counter satisfies a count threshold; and re-writing data of the first data track if a number of read errors detected during the reading of the first data track satisfies an error threshold.
 11. The method of claim 9, further comprising: resetting the track write counter of the first data track to a default value.
 12. The method of claim 9, further comprising: incrementing a track write counter of a third data track and a track write counter for a fourth data track responsive to the re-write of data of the first data track, the second data track and the third data track each separated from the first data track by one interlaced data track.
 13. A storage system comprising: a degradation management module configured to increment a track write counter of a first data track responsive to a data write command to a second data track but not increment any track write counters responsive to a data write to a second data track directly adjacent to the first data track.
 14. The storage system of claim 13, further comprising: a read/write management module coupled to a memory and configured to re-write data of the first data track and data of at least one data track directly adjacent to the first data track based on the value of the write track counter.
 15. The storage system of claim 13, wherein the first data track is directly adjacent to the second data track.
 16. The storage system of claim 14, wherein the degradation management module is further configured to reset the track write counter to a default value responsive to the re-write of data of the first data track.
 17. The storage system of claim 14, wherein the degradation management module is further configured to increase the track write counter of the first data track responsive to the re-write of the data of the at least one adjacent data track.
 18. The storage system of claim 14, wherein the degradation management module is further configured to increment a track write counter of a third data track and a track write counter for a fourth data track responsive to the re-write of the data of first data track, the third data track and the fourth data track each separated from the first data track by one interlaced data track.
 19. The storage system of claim 14, wherein the read/write management module re-writes data of the first data track before writing data of the at least one data track directly adjacent to the first data track. 